Conversation
|
Build successful! 🎉 |
|
Is a test possible for this one? |
|
I tried to make one but couldn't get it to fail in the SSR tests without the change unfortunately |
reidbarber
left a comment
There was a problem hiding this comment.
I still see the issue if I navigate to another page first, then the Picker page. Doesn't happen when just loading the Picker page first though.
|
oh thats bizzare, didn't expect that flow to break, I'll dig |
|
Build successful! 🎉 |
| enumerable: true, | ||
| value: function (node, child) { | ||
| if (this.dataset.reactAriaHidden) { | ||
| // child might not exist in this.content for some reason (stale?), add to end instead |
There was a problem hiding this comment.
???
In this case, what is the child and it's parent?
There was a problem hiding this comment.
oh, this seems wrong. <template> doesn't support direct children, they should be within the document fragment. That's what these overridden methods should be doing (since react doesn't handle that). So maybe we're missing another one and that's how those dives are getting there?
There was a problem hiding this comment.
ok I did some poking around and it seems like the monkey patches about didn't trigger their reactAriaHidden route when switching pages from some arbitrary page to the Picker docs page, hence causing the original error to appear when attempting to add a description via the example controls since we had stray direct children as you noticed above. I'm not 100% sure how that happens since the aria hidden data attribute should always be there...
On the plus side, this actually fixed a couple of tests that actually inadvertently noticed that those direct children were still appearing outside the document fragment.
|
Build successful! 🎉 |
1 similar comment
|
Build successful! 🎉 |
|
Build successful! 🎉 |

Closes #9376
✅ Pull Request Checklist:
📝 Test Instructions:
Go to S2 Picker docs. Type any description in the first example's description control, it should apply without crashing
🧢 Your Project:
RSP